DBM-6000 : Protocol Converter for the FAT2002 (Bosch Fire Central)

This protocol has been validated on a DBM-6000 ARM controller with an IP protocol converter. Interfacing has been developed with a Bosch FPA5000 unit coupled to a Fat2002 wich provide an interface to a telecommunication system conform to the ESPA 4.4.4 protocol.

Detectors and zones can be monitored for three states: disabled, fault or fire. There is no possibility for the DBM-6000 to arm or disarm a specified zone or detector. The converter only captures messages sent by the Fat2002 Panel to systems like pagers.

There are two version of the converter firmware. One with an auto reset mode (use it if the central re-sent the alarm message with an end string when the default ends) and one with a manual reset mode (use it if the central does not re-send the message when the default ends).

To interface a Bosch FPA5000 fire central to the DBM-6000, one Dinec Protocol Converter must be connected to a Fat2002 panel with an RS-232 serial cable.

A protocol converter can monitor up to 2000 points. This capacity is limited by the number of DinCool channels in the controller.

In the installation window, let us say that each item is a node.

1) How to set up the system
2) Configuration of the Converter node
3) Configuration of the Interface node
4) Configuration of the Messages node
5) Configuration of the Variables
6) Accessing variables with DinTalk
7) Connection control
8) Cabling RS-232
9) Screen examples

1) How to set up the system:

Add a protocol converter on the controller.
In the window “management of the devices on the main bus”, control that the model is "FAT2002AR/6000" or “FAT2002MR/6000” and the version is "3.30". If it is not the case, then burn the converter flash with the file named FT2AR_IP.S24 (AR letters are for Auto Reset) or FT2MR_IP.S24 (MR letters are for Manual Reset).
Add a single slave (address 0) on the converter: the Fat2002 Panel.
Add the messages sets. Each message is a zone and can contain detectors. You can also add a zone for the FPA5000, in our sample, the zone address is 3001.
Add the variables. The variable number 0 is for the whole zone. It is used especially when detectors have no logical address. Variables with numbers greater than 0 are detectors with logical address. See below for details.
TIPS:
- To set up the system quickly and in a safe way, start with one detector, set it up completely and verify its correct function. For the following detectors, use all possibilities of COPY/INSERT and COPY/PASTE on whole messages: it will create all the detectors for you.

2) Configuration of the Converter node:

Name	Fat2002 Converter	mandatory: a name to identify the protocol converter
Address	xxxx	mandatory: the serial number labelled on the protocol converter.
Protocol	Alarm Central	mandatory
Bauds	1200	mandatory
Bits	7	mandatory
Parity	Even	mandatory
Number Retry	-	This is the number of times the message is repeated before the converter generates a fault on the bus. Not use here.
Rx Time out	-	This is the time interval before repeating a message not acknowledged. Not use here.
Rx Time Ready	-	This is the delay before sending the next message after an acknowledge. Not use here.

3) Configuration of the Interface node:

The Fat2002 Panel with rs-232 serial interface is the only slave for the Converter node.

Name	A denomination for the Fat2002 Panel
Address	0
*Survey this connection*	Should be checked, or no alarm bus error will be generated.

4) Configuration of the Messages node:

A message is a zone. You can give a name at your convenience but the address must be correct.

*Name*	The zone name
*Address*	The number of the zone

5) Configuration of the Variables:

As seen before, the variables can be a 'Zone' if numbered 0 or a 'Detector' for greater numbers.

When you create a variable, this configuration popup is automatically displayed.

Later, when editing a variable properties, go in the 'Installator' sheet and click on 'Input properties' or select the variable in the variable list that can be accessed by a right-click on the 'Interface node' or the 'Converter node' (menu is 'Display the grid with the variables').

As for any other DinCool channel, you can set alarms for detectors. In case of alarm, it is immediate unless you made a inhibition.

Detectors and zones :

Name	the detector's name or the zone's name
Address	the detector's number or the zone's number

5.1 Channel properties:

States 0 to 3 are used. Set the following texts (or something at your best convenience but the meaning is) :

for Zones and Detectors:

0: Idle

1: Disabled

2: Fault

3: Fire

5.2 The default plan images :

	Not known
	Idle
	Default
	Fault and Fire

6) Accessing variables with DinTalk:

Add an external variable of type integer. Select the wanted channel in the list.

Possible integer values are 0 to 3 depending on the tag status.

7) Connection control:

Don't forget to set the 'Alarm on device offline' in the controllers properties.

If the protocol converter is disconnected, the converter detects the absence of communication and an error bus is generated immediately. The alarm programmed for main bus errors (if any) in the controller is started.

8) Cabling RS-232

Wiring : RS-232 cable: 3 wires

Protocol converter (Modbus port)	DB 9
RX (IN1)	3 (TX)
TX (IN2)	2 (RX)
GND	5 (GND)
	7 (RTS) shunted to 8 (CTS)
	4 (DTR) shunted to 6 (DSR)

See also the cabling diagrams in the general help of the DBM-6000.

9) Screen examples

In this example, five zones are defined. When the capture was made, there was a fire alarm on Detector 2/3 (zone = 2, detector = 3), so the variable 0 of the message 'Zone 2' that reflect the whole zone state has the same state.

As there is no message sent for the end of an alarm, state changes are only shown during 30 seconds and then Zone 2 and Detector 3 will return to Idle state.